home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
EuroCD 3
/
EuroCD 3.iso
/
Programming
/
Amos
/
AMOSList-0497
/
AMOSLIST
/
000165_amos-request@svcs1.digex.net_Sat Apr 19 18:36:43 1997.msg
< prev
next >
Wrap
Text File
|
1998-06-24
|
3KB
|
63 lines
Received: from svcs1.digex.net (svcs1.digex.net [204.91.197.224])
by mail2.access.digex.net (8.8.5/8.8.5) with ESMTP id SAA26033
for <mcox@access.digex.net>; Sat, 19 Apr 1997 18:36:42 -0400 (EDT)
Received: (from daemon@localhost)
by svcs1.digex.net (8.8.5/8.8.5) id RAA22577
for amos-out; Sat, 19 Apr 1997 17:10:04 -0400 (EDT)
Received: from mail2.access.digex.net (mail2.access.digex.net [205.197.247.3])
by svcs1.digex.net (8.8.5/8.8.5) with ESMTP id RAA22569
for <amos-list@svcs1.digex.net>; Sat, 19 Apr 1997 17:10:03 -0400 (EDT)
Received: from cpt6.stm.tudelft.nl (cpt6.stm.tudelft.nl [130.161.247.6])
by mail2.access.digex.net (8.8.5/8.8.5) with SMTP id RAA23212
for <amos-list@access.digex.net>; Sat, 19 Apr 1997 17:10:01 -0400 (EDT)
Message-Id: <199704192110.RAA23212@mail2.access.digex.net>
Received: by cpt6.stm.tudelft.nl
(1.38.193.4/16.2) id AA24279; Sat, 19 Apr 1997 23:08:10 +0200
From: "Maarten D. de Jong" <dejong@cpt6.stm.tudelft.nl>
Subject: Re: More bugs in AMOS
To: amos-list@access.digex.net
Date: Sat, 19 Apr 97 23:08:10 METDST
In-Reply-To: <Pine.SOL.3.96.970419202249.28123B-100000@kruuna.Helsinki.FI>; from "Joona I Palaste" at Apr 19, 97 8:25 pm
Mailer: Elm [revision: 70.85]
Status: RO
X-Status:
>
> Here's a collection of bugs or other curious things I have found in
> AMOS.
> - The AMOS classic manual states there is a command called Llist, which
> outputs the program code to the printer. This command does not exist.
There was a leaflet in my box of AMOS 1.2 stating that Llist never was imple-
mented, but that for some reason it was written about. The AMOS-way of Llist
is to go to the Blocks menu and select 'Print Block'. I forgot the details;
it's been awhile since I worked with AMOS.
> - Also in AMOS classic, I found that the command On Break Proc doesn't
> exist. This might have been fixed in AMOSpro, but I don't remember.
> - If you try to use user-defined functions as procedure parameters,
> e.g. MYPROC[FnA(123),FnB(456)] you get a "Illegal User Function" error.
> - You have to use a Wait Vbl after Dual Playfield to show it properly.
> This is not mentioned in the manual, or is it?
> Has anyone else experienced similar or other bugs? I'd like to know.
Scores. -2^3 yields 8 instead of -8 -- this was never fixed. Scrolling
DPF's with values which are not a multitude of one another (say, the first
with 'speed' 4 and the other with 3) leads to a annoying amount of flicker.
The windowing routines are buggy: clicking in an obscured part of a window
brings it to the front, even there is another window in front on that spot.
Print # in 1.36 can only cope with strings. Large arrays will start accessing
random locations if the index exceeds a certain number (I forgot which one).
There exists an off-by-one error in the Get Block command (I think -- it's
been five years at least since I wrote Mandarin about this one) which
requires you to specify a slightly different set of coordinates to get the
block you want. The editor can display erroneous text now and then.
Load Iff fails with large screens (>640x512).
I don't know the situation with AMOSPro, but I'm convinced it has its fair
share of bugs as well.
Regards,
Maarten